Support reading feature paths from the rerun formatter file #726
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
"@<file path>" as a feature path argument will result in that the file <file path> is read and the content interpreted according to the syntax created by the rerun formatter. If a feature path from the <file path> is not found on the file system, then it will be loaded from the classpath.
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR add support for reading the file created by the rerun formatter and running the scenarios specified there.
@<file path>as a feature path argument will result in that the file is read and the content interpreted according to the syntax created by the rerun formatter. If a feature path from the is not found on the file system, then it will be loaded from the classpath.This PR is build on top of #725.